My mother's computer (running XP Home Edition Build 2600 Svc Pk 2.0, IE 7.0) had numerous trojans, browser hijackers, and other malicious software hit it last week. After several days of virus scans from a boot cd, I was able to get back into windows. (The virus initially revealed itself by causing the Windows Logon screen to prevent logging on...it would logon for a split second, then immediately log off again.) Then IE would only allow access to her homepage, but would give me an error when trying to access any other page. A forced uninstall of IE 8 (which surprised me...her version of IE said it was 6) defaulted back to IE 7 and now that seems to be working fine. McAfee (provided by her ISP) would only show a blank screen - no menu to choose from. I don't even remember what I did to correct that, but it is now back and seems to work correctly according to McAfee's online Virtual Tech. Numerous virus scans (malicious software removal tool, Malwarebytes, SuperAntiSpyware, Kaspersky boot cd and live web scan, and McAfee) have finally turned up clean. However, on startup, once we reach the desktop, we continue to get a popup saying "c:\windows\opasohom.dll The specified module could not be found." I have researched this, and not even Google pulls up anything with that name. How can I change the startup so that windows doesn't try to load this bogus (I assume) file. Thank you!1 person needs an answerI do too

As a followup post, I found the opasohom.dll file in the Sys Config Utility under Startup. When trying to uncheck it, I get an "Access Denied" message saying I need to be logged on as Administrator to make that change, but then it unchecks it anyway. When I restart the computer, the Run DLL error popup doesn't happen, however the Sys Config Utility pops up saying that it is started in Diagnostic or Selective Startup mode and to run it in normal mode I need to change that on the Sys Configu General tab, which then undoes my change (and it re-checks the opasohom.dll file, which again gives me the popup error on startup.).

In the System Configuration Utility's Startup tab, what are the command and location associated with the item of concern? My suggestion would be to use e.g. regedit, if you're comfortable, to remove the reference to opasohom.dll from the location specified in MSCONFIG (System Configuration Utility). There are other ways to do it as well, if you are not comfortable with regedit, but it would be helpful to know the location, in that case.